For testing purposes, trying to install Exchange 2007 SP1 on a test Windows Server 2008 AD controller. I installed the following roles: Code Snippet ServerManagerCmd -i RSAT-ADDS ServerManagerCmd -i PowerShell ServerManagerCmd -i Web-Server ServerManagerCmd -i Web-ISAPI-Ext ServerManagerCmd -i Web-Metabase ServerManagerCmd -i Web-Lgcy-Mgmt-Console ServerManagerCmd -i Web-Basic-Auth ServerManagerCmd -i Web-Digest-Auth ServerManagerCmd -i Web-Windows-Auth ServerManagerCmd -i Web-Dyn-Compression When I attemp to add the exchange hub transport role, it fails to start the MSExchange Transport service. Afterwards the following errorsappear in the event log: Code SnippetProcess MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1852). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers. Code Snippet Microsoft Exchange couldn't read the configuration from the Active Directory directory service because of error: Failed to load config due to exception: Microsoft.Exchange.Data.Directory.NoSuitableServerFoundException: The Exchange Topology service on server localhost did not return a suitable domain controller. at Microsoft.Exchange.Data.Directory.DSAccessTopologyProvider.GetConfigDCInfo(Boolean throwOnFailure) at Microsoft.Exchange.Data.Directory.TopologyProvider.PopulateConfigNamingContexts() at Microsoft.Exchange.Data.Directory.TopologyProvider.GetConfigurationNamingContext() at Microsoft.Exchange.Data.Directory.ADSession.GetConnection(String preferredServer, Boolean isWriteOperation, Boolean isNotifyOperation, ADObjectId& rootId) at Microsoft.Exchange.Data.Directory.ADSession.GetReadConnection(String preferredServer, ADObjectId& rootId) at Microsoft.Exchange.Data.Directory.ADSession.Find(ADObjectId rootId, String optionalBaseDN, ADObjectId readId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, CreateObjectDelegate objectCreator, CreateObjectsDelegate arrayCreator) at Microsoft.Exchange.Data.Directory.ADSession.Find(ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, CreateObjectDelegate objectCtor, CreateObjectsDelegate arrayCtor) at Microsoft.Exchange.Data.Directory.ADSession.Find[TResult](ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties) at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.Find[TResult](ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults) at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.FindServerByFqdn(String serverFqdn) at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.FindLocalServer() at Microsoft.Exchange.Transport.LocalServerConfiguration.<>c__DisplayClass2.b__0() at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount) at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount). This error is greek to me. What troubleshooting steps should I take so that the hub / mailbox roles are sucessfully installed? thanks!

Hello, Looks like IPv6 is not enabled on the server, try to install after enabling it. Installing Exchange 2007 SP1 on Windows 2008 RTM http://www.exchangeinbox.com/article.aspx?i=111

Amit Tank wrote: Hello, Looks like IPv6 is not enabled on the server, try to install after enabling it. Installing Exchange 2007 SP1 on Windows 2008 RTM http://www.exchangeinbox.com/article.aspx?i=111 Wow, I didn't even have IP V6 setup but guess it was enough to screw up the Exchange 2007 install. I used the following KB article to disable via the registry. http://support.microsoft.com/?kbid=952842 Perhaps, a future Exchange 2007 install will be kind enough to warn us up front

Just one more caveat to add to the list of Server 2008/Exchange 2007 quirks. I had an issue just the other day with DNS lookups in Exchange 2007. The fix? Disable IPv6. Now, I'm having the same issue that this topic is about - and the fix is to renable IPv6. Me thinks QC has really gone to ____ since Bill's not around.